Secure key management

ABSTRACT

According to one embodiment, a method for implementing secure key management is provided. The method includes populating a section of information associated with a key, the section being populated with information relating to how the key was created. The method also includes populating the section with information relating to how the key was acquired by a secure module; and binding the section to the key, wherein the key is encrypted.

CROSS-REFERENCE TO RELATED APPLICATION

The present disclosure is a continuation of U.S. patent application Ser. No. 13/100,354, entitled “SECURE KEY MANAGEMENT,” filed on May 4, 2011, which is incorporated herein by reference in its entirety.

BACKGROUND

The present invention relates to data processing, and more specifically, to cryptography methods to enhance security of keys.

Keys may pass through a number of forms, and corresponding levels of protection, during the life cycle of the key. In cryptographic systems, knowledge of the current state, and corresponding protection level, of the key may be insufficient to determine if a key is suitable for a selected secure task.

SUMMARY

According to one embodiment of the present invention, a method for implementing secure key management is provided. The method includes populating a section of information associated with a key, the section being populated with information relating to how the key was created. The method also includes populating the section with information relating to how the key was acquired by a secure module; and binding the section to the key, wherein the key is encrypted.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 depicts a block diagram of a system upon which secure key management methods may be implemented in an exemplary embodiment;

FIG. 2 depicts a block diagram of a token or data structure to manage key material;

FIG. 3 depicts a block diagram of a header section of the token of FIG. 2;

FIG. 4 depicts a block diagram of a wrapping information section of the token of FIG. 2;

FIG. 5 depicts a block diagram of an associated data section of the token of FIG. 2;

FIG. 6 depicts a block diagram of a payload section of the token of FIG. 2; and

FIG. 7 depicts a block diagram of an exemplary system for recording and storing information relating to the creation of a key and acquisition of the key.

DETAILED DESCRIPTION

Exemplary embodiments of the invention provide for the secure management of keys (also called “key material”) comprised of one or more key parts. Embodiments may use a token (also called “key tokens”) or other suitable structure or device for key material management. An exemplary token is a data structure that can hold a complete or partial cryptographic key along with a key's management and usage information associated with the key. The exemplary embodiments create, utilize and update sections of the token structure to perform various tasks including management of the key and storing information relating to the key, including associated information related to creation of the key, acquiring the key and/or a level of key protection accumulated over time. By having the information securely bound to the key itself, the trustworthiness of the key can be established, thereby enabling the user to determine if the key is suitable for a selected task.

In an embodiment, the information associated with and bound to the key may be removed from the token by a secure module, described below, for accessing and updating the information within the secure module. After accessing the information and/or key, the information and key are placed back inside the secure key token before sending the token to a location outside the module. While being accessed inside the secure module the key and associated information (also called “key control information” or “associated data”) section remain connected or bound to one another in some fashion.

It should be understood that the systems and methods for key management, including populating and updating the associated data section securely bound to the key, may be used for a structure including a key with a relationship with the associated data, metadata and/or information. The methods and systems utilize a suitable arrangement to securely bind the key to information that describes events that occur during the life of the key. One arrangement may utilize the key token structure described below.

With reference now to FIGS. 1 and 2, an exemplary system 100 and token 200 for providing secure key management will now be described. The exemplary system 100 creates, uses and/or transmits key tokens and/or key material. The system of FIG. 1 includes a user system 102 in communication over one or more networks 104 with a host system 106. The user system 102 represents a first party that submits key material to be communicated to a second party (e.g., the host system 106). The user system 102 may be a point of sale (POS) terminal that is implemented using a computer executing a computer program for carrying out the processes described herein. The user system 102 may include a hardware security module (HSM), such as a card, software and firmware configured to create, populate and manage the token 200 containing the key material as described herein. An HSM may be described as a piece of hardware and associated software/firmware that acts as a highly secure peripheral device, or secure cryptoprocessor, for the management of cryptographic keys and for the protection of sensitive data and applications.

In the depicted embodiment, an application 108 is used by the HSM on the host system 106 to create, populate and manage the token 200. The user system 102 may be a payment terminal, such as an automated teller machine (ATM) or kiosk, configured to receive user information, such as account information or account PIN. The host system 106 may be a financial institution connected to the user system 102 via one or more of the network(s) 104. The key material resides in a token in storage within the host system 106. The financial institution receives encrypted data from the terminal user system 102 over the network 104, which may include an account number and PIN information. Then the application 108 retrieves the key material from local storage and passes it into the HSM along with the received encrypted data. Inside the HSM, the token with the key material is unwrapped and the unwrapped key from the token is then used to decrypt the encrypted data from user system 102. The data can then be checked and verified, which is then communicated to the application 108. In one exemplary embodiment, the user system 102 includes hardware and software to execute computer instructions to create the token 200 that securely wraps the key material for local use or for transmission to another party, such as the host system 106. In another exemplary embodiment, the host system 106 executes computer instructions to create the token 200 that securely wraps the key material for local use or for transmission to another party, such as the user system 102.

The network(s) 104 may be any type of known networks including, but not limited to, a wide area network (WAN), a local area network (LAN), a global network (e.g. Internet), a virtual private network (VPN), and an intranet. The network 104 may be implemented using a wireless network or any kind of physical network implementation known in the art. The user system 102 may be coupled to the host system 106 through multiple networks (e.g., intranet and Internet). One or more user systems 102 and the host system 106 may be connected to the network 104 in a wired or wireless fashion. In one embodiment, the network 104 is an intranet and one or more user systems 102 execute a user interface application (e.g., a web browser) to contact the host system 106 through the network 104. In another exemplary embodiment, one or more of the user systems 102 is connected directly (i.e., not through the network 104) to the host system 106.

The host system 106 depicted in FIG. 1 may be implemented using one or more servers operating in response to a computer program stored in a storage medium accessible by the server. The host system 106 may include one or more hardware security modules (HSM), such as a card, software and firmware configured to create and manage tokens containing the key material as described herein.

The exemplary secure key management methods and structures may be created and performed by components of the system 100 of FIG. 1.

The token 200 may reside locally on and be created by the host system 106 or user system 102. For example, the user system 102 may include a token 200 containing key material used to encrypt account data to send to the host system 106. In this embodiment, the token 200 is a data structure that includes several sections (e.g., sections 300, 400, 500 and 600) dedicated to selected tasks such as describing the token and key material. A header section 300 includes data used to interpret fields within sections of the token 200. The exemplary header section 300 is a fixed-size section of the token 200. A wrapping information section 400 is also a fixed-size section that contains information pertinent to how (and if) the key material in a payload section 600 is wrapped. The wrapping information section 400 also includes information about how the key material in the payload section 600 is securely bound to the information in an associated data (AD) section 500. The associated data section 500 may also be described as a key control information section, wherein the section contains fields configured to store various types of information, such as a user-defined data to be associated with the key material. The associated data section 500 is a variable-size section that has a small fixed-size portion with some descriptive fields for the key material itself, along with length fields for the variable-size portions of this section.

The payload section 600 is where the key material resides in a selected state. In an example, there are three states, including (1) not present, (2) clear and (3) encrypted/bound. In the not present state, the token is a “skeleton” which contains descriptive and policy information in a useful template that can be populated into a specific token with key material at a later time. The clear state may be used for testing purposes or low security applications, where it is useful to support tokens that have unencrypted key material. In the encrypted/bound state, the key material is accompanied with pre-pended and/or post-pended data (key binding material). The key material and pre-pended or post-pended data conforms to and is wrapped using a supported wrapping method indicated by token fields within the wrapping information section 400. The exemplary token 200 enables wrapping of the token sections via a suitable wrapping method, as described below, without altering the token 200 structure. Specifically, the structure of the header 300, wrapping information 400 and associated data 500 sections will not change based on the chosen wrapping method.

The sections of the exemplary token 200 may have fixed or variable sizes. For example, the header section 300 has the fixed size of 8 bytes and the wrapping information section 400 has the fixed size of 22 bytes. The associated data section 500 has an overall variable size composed of the fixed-size portion of 16 bytes plus a sum of variable-sized other portions of the section. Similarly, the payload section 600 has a variable-size depending on the state of the key material. Exemplary payload sizes include: 0 bits for tokens with no key material; the length of the key itself for unencrypted key material; and the length of the key plus the length of the key binding material for tokens that include encrypted key material.

Turning now to FIG. 3, the exemplary header section 300 of the token 200 will now be described. The header section 300 includes several fields used to describe aspects of the token 200. A token identifier field 302 indicates broad token type information to aid processing of the token 200. Token types that may be listed in the token identifier field include internal tokens for local use, external tokens for sending to another party, or zero token types, depending on usage needs and application requirements. A zero token is typically a placeholder, which may be a string of one or more bytes with all zero bits in the first byte, which is passed into an application program interface in a position that a full token is expected in return. A reserved field 304 is set aside for future use. An overall token length field 306 indicates the entire length of the token 200, including the header section 300. A token version number field 308 describes a version of the token 200, which separates this token from legacy token structure types supported by systems from the same manufacturer as the current system 100. This enables the system 100 to access and use current and legacy token types on the same machines. A reserved field 310 is also set aside for future use.

FIG. 4 shows the exemplary wrapping information section 400 which includes fields to describe how the key material in the payload section 600 is wrapped and secured to the associated data section 500 (key control information). A key material state field 402 describes a state of the key material in the payload section 600. Possible states include: no key present; the key is clear; the key and a representation of the key control information, such as a hash, is encrypted under a Key Encrypting Key (KEK); and the key and a representation of the key control information, such as a hash, is encrypted under the secret Master Key (MK) that stays in the HSM.

In the no key present state, the token is a “skeleton” which contains descriptive and policy information in a useful template that can be populated into a specific token with actual key material at a later time. The clear state is used for testing purposes or low security applications. In the encrypted state of KEK and MK, the key material is wrapped and bound by key binding material. The states available in the key material state field 402 are limited by the token identifier field 302, wherein an external token identifier may have a key material state of no key, a clear key or a KEK encryption. Similarly, an internal token identifier may have a key material state of no key, a clear key or an MK encryption. Accordingly, the KEK key material state is used to send the key material to another party, whereas the MK key material state is used locally by a host application.

With continued reference to FIG. 4, the wrapping key verification pattern (KVP) type field 404 specifies the calculation method, such as a cryptographic hash algorithm (also referred to as “hash algorithm”), to apply to the MK or KEK (as described in key material state field 402) used to wrap the payload field 600. The output of the calculation is then compared to the content of a wrapping KVP value field 406 to verify that the correct key has been identified as wrapping the payload section 600. If the values do not match, then the wrong key has been provided and the user is notified of the error. The KVP type field 404 and wrapping KVP value field 406 are not used if the key material state is no key or clear key.

A wrapping method field 408 is used to describe the payload section 600 wrapping method and how it is bound to the associated data section 500. In an embodiment, the user selects, via the HSM, the wrapping method to use when the token 200 is created. This wrapping method can include the layout of the payload section 600, the logical operations to perform on the key used for encryption, such as KEK or MK, and what steps to do with the key used for encryption to make up the final payload section 600, such as additional encryption steps or operations to bind associated data into the secure payload. The logical operations to perform on the key used for encryption are various steps performed in wrapping the payload section 600. As many as 255 wrapping methods can be described. In one embodiment, four values are assigned to corresponding wrapping methods. Examples of wrapping methods include advanced encryption standard key wrap (AESKW) or a public key encryption scheme that combines algorithms, such as RSAES (Rivest Shamir Adelman Encryption Scheme) with OAEP (Optimal Asymmetric Encryption Padding).

A hash method field 410 describes a hash algorithm applied to the associated data section 500, wherein the resulting hash value is then compared to a stored hash value (field 610) in the payload section 600. This check against the stored value is a mechanism to indicate if the associated data section 500 has been altered. A reserved field 412 is set aside for future use.

Referring now to FIG. 5, the exemplary associated data (AD) section 500 (also referred to as “key control information section” or “associated information section”) includes fields used to describe attributes of the key material and other fields to describe field sizes in this section. An AD version field 501 is used to identify the version of the current AD section 500, thus allowing for future expansion as well as support across multiple versions and layouts. A reserved field 502 is set aside for future use. In addition, reserved fields, in this and other sections, may be utilized to enable alignment of data in the section. A total length of AD field 504 describes the size of the AD section 500, thereby enabling the section to vary in size. A length of AD label field 506 describes the size of an optional AD label field 526 that is passed by the user. In an example, this field gives the label length in bytes wherein the length is either 64 or 0. A length of proprietary data field 508 describes a length in bytes of an extensible proprietary data field 528 (0-255) contained in the AD where the data is placed by the manufacturer of the HSM (either where the token is created or currently resides), such as control and tracking data outside the other data fields. A length of user data field 510 describes the size of an extensible user data field 530, wherein the user can populate the variable length field (0-255) via a provided interface, such as an API for the system. A reserved field 512 is set aside for future use.

A bit length of payload field 514 describes the length of the payload section 600 in bits, which is important for certain wrapping methods used to protect the payload. A reserved field 516 is set aside for future use. A cryptographic algorithm identified in key field 518 indicates which supported cryptographic algorithm can be used with the encrypted key material in the payload. Examples of the algorithm include those used with the following standards: AES, data encryption standard (DES), RSA, Elliptic Curve and message authentication code (MAC). A type of key field 520 defines the categories for use of the key material with the algorithm from field 518. Categories of use are broad and include cipher key, importer KEK, exporter KEK, and MAC. Key usage fields (KUFs) 522 are a variable length and extensible field or set of fields that define narrower attributes for the key type defined in 520. Exemplary attributes in the key usage fields 522 describe how the key material can be used and/or limits actions that may be performed in various situations available for this key type. For example, if the key material is an AES key for importing or exporting other keys, it can be used as a wrapping key for exporting other AES keys from this HSM or as an unwrapping key to import other AES keys into this HSM. In another example, if the key material is a cipher key, the key usage fields 522 can further limit key material use to enciphering or deciphering. A plurality of usage description fields may be placed in the set of key usage fields 522. Accordingly, the key usage fields 522 vary in size and interpretation based on other fields, such as fields 518 and 520. The exemplary key usage fields 522 are in the following format—one byte: count of fields that follow this byte; two bytes each: fields with key usage fields data.

Still referring to FIG. 5, key management fields (KMFs) 524 are a variable length and extensible field or set of fields that define attributes of the key material wrapped in the token, including but not limited to what type of KEKs can be used to wrap this key material (if any), whether the wrapped key material is complete or expects more user contributed material, how the key was created, how the key was acquired by the current module and information relating to the protection of the key over time. Other examples of attributes include limiting what can be done to the key material, such as limiting distribution or export of the key material, such as a cipher key, after receipt of the key material by a party. The number of attributes or entries in the key management fields 524 is variable. The key management fields 524 vary in size and interpretation based on other fields, such as fields 518 and 520. Exemplary key management fields 524 are in the following format—one byte: count of fields that follow this byte; two bytes each: fields with key management fields data. In an embodiment, described in further detail below, exemplary key management fields 524 include fields that allow user policies to be implemented to manage and record the entire key material life cycle and are extensible to register key history and policies for the remaining key life cycle. For example, the fields allow updating of life cycle information after receiving the key material. Further, policies may be created after receipt to specify when the key material is to be retired or allowable methods for wrapping the key material itself.

As discussed above, the AD label field 526 is a user specified optional field that gives a meaningful name to the token 200. An exemplary AD label field 526 is 64 bytes. The label is within the token 200, thereby enabling recovery of the label via field 526. Further, the AD label field is securely bound to the key material due to being wrapped as part of the AD section 500 with the key material. In addition, since the label is unencrypted, it can be used by the host system to check if the user is authorized to use the key token. The proprietary data field 528 is for the HSM provider to include their own data or identifiers, which will be securely bound to the key material if an appropriate wrapping method is selected. The user data field 530 is for user populated data and may hold data as designated by the HSM—using host application. Accordingly, the user populates the data using an interface on a host application. The optional sections fields 532 allow for further extensibility of the token 200 at the discretion of the HSM—using host application or the HSM manufacturer. Each optional section field is in the format of unique identifier, length (must include length of identifier and length fields) and an optional data section.

Referring now to FIG. 6, the exemplary payload section 600 may have no content, or may not be wrapped (key material is here by itself and is not encrypted). If the payload section 600 contains wrapped content then fields 408 and 410 can be used to interpret the payload contents and the method for using the appropriate KEK or MK to unwrap the payload. As stated above, the payload section 600 layout depends on the wrapping method chosen, such as AESKW or RSAES-OAEP wrapping methods. Moreover, the structure and layout of the header section 300, wrapping information section 400, associated data section 500 and payload section 600 are independent and remain the same as the wrapping method for the token 200 and payload section 600 are changed. As an example, the AESKW wrapping method and corresponding payload layout will be described.

The integrity check constant value field 602 includes a known constant that is used to determine if the unwrap succeeded before looking at other fields in the section. If the constant is not correct then the payload and/or its associated data were corrupted or modified in some way outside the control of the HSM. The corruption or modification is then alerted to the user. A bit length of padding field 604 is used to describe if there is padding and the size of padding, depending on the bit length of the key material in the payload. Thus, this field indicates how much padding to remove. A length of hash options field 606 describes the length of a hash options field 608. The hash options field 608 describes various options that may be used in computing the hash of AD field 610, while still conforming to the AESKW standard. The hash of AD 610 is the hash value of the AD section 500, used to verify that the section has not been altered. A clear key material field 612 contains the key material or secret key that is carried in the payload section 600. A key padding field 614 is used to pad the key material and depends on the size of the key material in field 612.

In embodiments, the key in the token 200 is created outside of or within a local system, such as host system 106 (FIG. 1). The host system 106 includes a secure module, such as an HSM, wherein creation of the key within the secure module provides a user with knowledge of the key's protection level from the time of it's creation. Therefore due to the access to the history of the key's protection level, the trustworthiness of the key can be simply established, enabling the user to decide what actions, tasks and/or applications are appropriate for the key.

In embodiments where the key is created outside the local system, the key protection level prior to entry into the local system may be unknown. The unknown level of key protection would not indicate if an exposure of the key has occurred outside the HSM. Therefore, the unknown key protection level reduces the trustworthiness level of the key, limiting the number of tasks or actions that the key is appropriate for. Embodiments of the key and information related to the key using the key token structure described above provide information relating to the key creation as well as information about how the key was imported. Further, the information (i.e., associated data section) may include a cumulative record of the protection level of the key over time. Systems and processes that utilize keys and structures that provide this information enable the user to ascertain the trustworthiness of the key and limit use of the key based on the information provided. Accordingly, the associated data section (key control information or key control information section) securely bound to the key provides enhanced security for the key. In an embodiment, operations to access and populate the associated data section are only performed within the secure module, thus ensuring that the associated data section cannot be altered by an unauthorized party. In an embodiment, the associated data section may be in the clear or may be encrypted, but may not be altered outside the HSM.

Embodiments of the secure system, such as system 100 (FIG. 1), are discussed below where the system manages keys and stores the associated information relating to the key protection level, the key creation and/or the acquisition of the key by the local system. In an embodiment, the system 100 includes a secure module, such as an HSM, in the host system 106. The HSM in the host system 106 is configured to access the key and associated information that are securely bound together as part of token 200. Exemplary systems and methods may use any suitable data structure, token and/or hardware to provide a secure binding between the key and the associated information, wherein the information is updated within the HSM. For ease of explanation, the method and system below will be described with reference to the token 200 of FIGS. 2-6, although any suitable structure or token configuration may be used.

FIG. 7 is a block diagram of an exemplary system and method 700 for recording and storing information relating to the creation of a key and acquisition of the key. A first example 702 of the method and system illustrates a key being created on another system (i.e., non-local system) configured to support saving and storing the key creation and acquisition information. A second example 704 shows key creation on a non-local system that does not support recording the key creation and acquisition information. In addition a third example 706 illustrates key creation on a local system, including a secure module 712 (i.e., HSM), where the key is also being used on the system. In embodiments, the key and information relating to the creation and acquisition of the key by the current secure module are stored in the key token 200. Further, the information relating to the creation and acquisition of the key is stored in the key management fields 524 of the associated data section 500 (also referred to as “key control information”).

Referring to the first example 702, in the first block 708, a section of information securely bound to and associated with the key is populated with the information relating to the key creation. In an embodiment, the key creation information is securely stored in the extensible key management fields 524 (KMF). The information as to how the key was generated or created is attached to the key for life and is used to determine if the key can be trusted to perform certain actions in the future. Therefore, an import block 710 illustrates that the key and the key creation information (associated information) are imported into 712 secure module 712 of the local system. In the embodiment, a common format is used by the local and non-local systems to enable importing of the key creation information to the secure module 706. Further, during the import block 710 (also called the acquiring step), the information describing how the key was imported by the secure module 712 is added to the associated information. In the next step, the secure module 712 stores the securely bound key creation information, the key acquisition information and the key itself in a local key store 714.

Referring now to the second example 704, a block 716 represents key creation on a non-local system that does not support storing the key creation information. Thus, the key is created and imported, as shown by an import block 718, without information relating to the key creation. As the key is imported, information about how the key was acquired by the module is attached by the secure module 712 to the key, as shown by add information block 720. Therefore, the import block 718 and add information block 720 are performed with the secure module 712 to establish a secure binding between the key and the key acquisition information. Although the secure module 712 supports storing all of the associated data, the key will have information describing how the key was acquired but will not have key creation information. An exemplary key creation value for the key management field 524 in the key store 714 for a key created in the second example 704.

Referring now to the third example 706, a block 722 shows that the key is created within the secure module 712 for use within the local system. Accordingly, as the key is generated or created, the key creation information and key acquisition information are stored in the key store 714. In an embodiment, the key creation information and key acquisition information are one input or are two inputs with the same value, as the key is acquired as it is created by the secure module 712. Accordingly, information describing how the key was acquired also describes how it was created.

Thus, the system and method 700 provide a secure binding between the key and the associated key creation and acquisition information for each of the examples 702, 704 and 706. In embodiments, the key may be encrypted or unencrypted within the secure module 712, however the key is encrypted when outside the module. The key and associated information are then stored in the key store 714 within the secure module 712, wherein the information may be accessed to indicate a trustworthiness of the key. The system and secure module may determine which activities the key is suited for based on the key creation and/or key import information. The key creation information in the key store 714 may include any information related to the key creation, such as any of the following non-limiting examples: the key was randomly generated on the originating system; the key was created by several key parts each provided by different parties; and the key was created from a value entered into the originator system by a single party. The key creation information is attached to the key for the key's life cycle and may be accessed by any system that supports the data structure (e.g., token 200) that includes the associated information (e.g., KMF 524 in the AD section 500) securely bound to the key itself. Further, the key management fields 524 may be extensible, thereby providing flexibility for the stored key creation and key acquisition information.

The key acquisition information may include any information related to how the key was imported into the secure module 712, such as any of the following non-limiting examples: the key was imported to the system from a structure (i.e. a key token) that supports the structure with the key creation and import information and, thus, includes the key creation information; the key was imported using a selected encryption method (e.g., RSA, OAEP, etc.) wherein the key does not have key creation information; and the key was input in a number of key shares created using a secret sharing algorithm.

In embodiments the key control information, including the key creation and key acquisition information are populated securely within the secure module (i.e., HSM). Further, the key control information is securely bound to the key when outside the secure module by a suitable structure, such as the key token 200. In embodiments, the key control information is not encrypted outside of the secure module, thereby enabling systems to access, but not alter, the information, which can be used to determine the key's trustworthiness.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one more other features, integers, steps, operations, element components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated

The flow diagrams depicted herein are just one example. There may be many variations to this diagram or the steps (or operations) described therein without departing from the spirit of the invention. For instance, the steps may be performed in a differing order or steps may be added, deleted or modified. All of these variations are considered a part of the claimed invention.

While the preferred embodiment to the invention had been described, it will be understood that those skilled in the art, both now and in the future, may make various improvements and enhancements which fall within the scope of the claims which follow. These claims should be construed to maintain the proper protection for the invention first described. 

1. A method for secure key management, comprising: populating a section of information associated with a key, the section of information being populated with information relating to how the key was created; populating the section of information with information relating to how the key was acquired by a secure module; and binding the section of information to the key, wherein the key is encrypted.
 2. The method of claim 1, wherein populating the section of information associated with the key comprises populating a key control information section of a key token, the key token including the key.
 3. The method of claim 2, wherein the key control information section comprises a key management field.
 4. The method of claim 2, wherein the key control information section and the key are located in the key token outside the secure module and the key control information section is not encrypted when outside the secure module.
 5. The method of claim 1, comprising enabling an action for the key based on at least one of the information relating to the how the key was created and information relating to how the key was acquired.
 6. The method of claim 1, wherein the section of information comprises extensible fields.
 7. The method of claim 1, wherein populating the section of information occurs within the secure module.
 8. The method of claim 1, wherein populating the section of information with information relating to how the key was acquired by the secure module occurs as the key is received by the secure module.
 9. The method of claim 1, wherein populating the section of information with information relating to how the key was created comprises one of importing the information related to how the key was created as the key is imported into the secure module or populating the information related to how the key was created as the key is created in the secure module. 